Skip to content

1268 Vaccination data reporting expired #1269

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

HenrZu
Copy link
Contributor

@HenrZu HenrZu commented Apr 28, 2025

Changes and Information

Please briefly list the changes (main added features, changed items, or corrected bugs) made:

  • Since vaccination data is no longer reported since July 24, we dont need it to init the model for days after.
  • DIVI data has continued to be reported. Therefore, we can enable the usage for days after July 24 again.

If need be, add additional information and what the reviewer should look out for in particular:

Merge Request - Guideline Checklist

Please check our git workflow. Use the draft feature if the Pull Request is not yet ready to review.

Checks by code author

  • Every addressed issue is linked (use the "Closes #ISSUE" keyword below)
  • New code adheres to coding guidelines
  • No large data files have been added (files should in sum not exceed 100 KB, avoid PDFs, Word docs, etc.)
  • Tests are added for new functionality and a local test run was successful (with and without OpenMP)
  • Appropriate documentation for new functionality has been added (Doxygen in the code and Markdown files if necessary)
  • Proper attention to licenses, especially no new third-party software with conflicting license has been added
  • (For ABM development) Checked benchmark results and ran and posted a local test above from before and after development to ensure performance is monitored.

Checks by code reviewer(s)

  • Corresponding issue(s) is/are linked and addressed
  • Code is clean of development artifacts (no deactivated or commented code lines, no debugging printouts, etc.)
  • Appropriate unit tests have been added, CI passes, code coverage and performance is acceptable (did not decrease)
  • No large data files added in the whole history of commits(files should in sum not exceed 100 KB, avoid PDFs, Word docs, etc.)
  • On merge, add 2-5 lines with the changes (main added features, changed items, or corrected bugs) to the merge-commit-message. This can be taken from the briefly-list-the-changes above (best case) or the separate commit messages (worst case).

Copy link

codecov bot commented Apr 28, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.22%. Comparing base (672cbc1) to head (f3860b6).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1269   +/-   ##
=======================================
  Coverage   97.21%   97.22%           
=======================================
  Files         156      156           
  Lines       14674    14709   +35     
=======================================
+ Hits        14266    14301   +35     
  Misses        408      408           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@HenrZu HenrZu linked an issue Apr 28, 2025 that may be closed by this pull request
2 tasks
@HenrZu HenrZu requested a review from annawendler April 29, 2025 07:21
@HenrZu HenrZu changed the title 1268 Vaccination data is outdated 1268 Vaccination data reporting expired Apr 29, 2025
Copy link
Member

@annawendler annawendler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code looks good and is consistent in itself. I was wondering why you chose to implement the functionality to set the vacc data to zero in this set_vacc_data() function and not the other one. When you implement it like this it is unclear to me what happens if the simulation interval is only partially contained in the vacc dates. Here https://github.com/SciCompMod/memilio/blob/main/cpp/models/ode_secirts/parameters_io.h#L866 you are already mentioning that for the dates after the end of vacc_data you set the values to 0 but I don't findwhere this is actually done. Also I don't understand why you don't throw a similar warning for the respective min_date, can you explain?

@@ -666,14 +661,14 @@ TEST(TestOdeSECIRVVS, read_data)

auto read_result1 = mio::osecirvvs::read_input_data_county(model1, {2020, 12, 01}, {1002},
std::vector<double>(size_t(num_age_groups), 1.0), 1.0,
TEST_GERMANY_PYDATA_DIR, 10);
TEST_GERMANY_PYDATA_DIR, 30);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you change this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I initially wanted to write a comment regarding this here :D
The vaccination data for the tests is completely synthetic and starts on 1 October. If we only look 10 days in the future, then is_vaccination_data_available would return false and no vaccination data would be set. If I set this to 30, then the vaccination data is set because it then returns true ;)
that might be a bit confusing, but it would solve the problem for now. I will adjust the synthetic data in a future pull request to make this more realistic.

@HenrZu
Copy link
Contributor Author

HenrZu commented May 21, 2025

I was wondering why you chose to implement the functionality to set the vacc data to zero in this set_vacc_data() function and not the other one.

Because the other function requires the vaccination data. So, if the data is not available, we dont need to read in the vaccination data.

@HenrZu
Copy link
Contributor Author

HenrZu commented May 21, 2025

Here https://github.com/SciCompMod/memilio/blob/main/cpp/models/ode_secirts/parameters_io.h#L866 you are already mentioning that for the dates after the end of vacc_data you set the values to 0 but I don't findwhere this is actually done

in the secirvvs model, if data in future is not avialable, we do some linear continuation based on the last entries. If the Simulation
is starting before vaccinations are available, they are set to Zero.

In the secirts model, we set all vaccinations to Zero, before and after the vaccination data is avail.
Here

if (date_df == offset_full_date) {

we only set if data is avail. For Dates after, we go in the else loop. FOr all Dates before, we have already initialized it with Zero in
model[i].parameters.template get<DailyPartialVaccinations<FP>>()[{g, d}] = 0.0;

@HenrZu HenrZu requested a review from annawendler May 21, 2025 11:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Vaccination data is outdated since july 2024
2 participants